Reduction of processing overhead for point in time copy to allow access to time locked data

ABSTRACT

A computational device generates a point in time copy of one or more regions of a time locked data set, in response to receiving one or more I/O operations directed to the time locked data set. The one or more I/O operations are performed on the point in time copy of the one or more regions of the time locked data set, in response to generating the point in time copy of the one or more regions of the time locked data set.

BACKGROUND 1. Field

Embodiments relate to reduction of processing overhead for point in timecopy to allow access to time locked data.

2. Background

In certain storage system environments, a storage controller (or astorage controller complex) may comprise a plurality of storage serversthat are coupled to each other. The storage controller allows hostcomputing systems to perform input/output (I/O) operations with storagedevices controlled by the storage controller, where the host computingsystems may be referred to as hosts.

In many systems, data on one storage device may be copied to the same oranother storage device so that access to data volumes may be providedfrom two different locations. Point in time copy allows creation ofinstantaneous, point in time snapshot copies of entire logical volumesor data sets. A point in time copy may involve physically copying allthe data from a source volumes to a target volume so that the targetvolume has a copy of the data as of a point in time. A point in timecopy may also be generated by logically creating a copy of the data andthen copying data over only when necessary. A point in time copyoperations may also be referred to as flash operations. FlashCopy* (FLC)is a type of point in time copy in which nearly instantaneous point intime snapshot copies of entire logical volumes or data sets may becreated.

A time lock is a mechanism that locks data for a period of time. U.S.Pat. No. 9,218,295 describes a method for implementing time locks. U.S.Pat. No. 8,185,754 describes a method for time-based storage access.U.S. Pat. No. 7,313,557 describes a multi-protocol lock manager thatmanages granting, revoking and releasing of various types of locks onfiles. U.S. Pat. No. 7,010,493 describes a method for managing access tostorage resources according to an access time. US patent publication2015/0363125 describes a method for executing a copy-offload operation.U.S. Pat. No. 9,075,762 describes a method for setting copy permissionsfor target data in a copy relationship. U.S. Pat. No. 8,954,408describes a method for allowing writes to complete without obtaining awrite lock to a file. US patent publication 2006/0095682 describes amethod for lock management for a flash copy image of a region of data inN-way shared storage system.

SUMMARY OF THE PREFERRED EMBODIMENTS

Provided are a method, system, and computer program product in which acomputational device generates a point in time copy of one or moreregions of a time locked data set, in response to receiving one or moreI/O operations directed to the time locked data set. The one or more I/Ooperations are performed on the point in time copy of the one or moreregions of the time locked data set, in response to generating the pointin time copy of the one or more regions of the time locked data set. Asa result, lesser processing time and fewer storage resources may beneeded for point in time copy generation, relative to situations inwhich a point in time copy is made of the entirety of the time lockeddata set. Additionally, I/O operations are allowed to be performed evenwhen the data set is time locked.

In additional embodiments, the one or more regions comprise an entiretyof the time locked data set. As a result, a point in time copy is madefor the entirety of the time locked data set.

In further embodiments, the one or more regions comprise those regionsof the time locked data set to which the I/O operations are directed.The point in time copy is generated for a part of the time locked dataset, and as a result the time for generating the point in time copy isreduced over situations in which a point in time copy is generated forthe entirety of the time locked data set.

In certain embodiments, the generating of the point in time copy of theone or more regions of the time locked data set is performed subsequentto the one or more I/O operations exceeding a predetermined thresholdnumber. As a result, the time consuming task of performing the point intime copy operation for a large volume or volumes is delayed until asufficient number of I/O operations are pending.

In further embodiments, the computational device prevents the I/Ooperations to be performed on the time locked data set. As a result, thetime locked data set is protected against access.

In certain embodiments, the one or more regions include one or morevolumes or parts of volumes in which the time locked data set is stored.As a result, volumes of parts of volumes are used to generate the pointin time copy.

In further embodiments, on expiry of a time lock on the time locked dataset, additional I/O operations are directed to the time locked data setand not directed to the point in time copy. As a result, the data set isno longer protected from access after expiry of the time lock.

BRIEF DESCRIPTION OF THE DRAWINGS

Referring now to the drawings in which like reference numbers representcorresponding parts throughout:

FIG. 1 illustrates a block diagram of a computing environment comprisinga storage controller coupled to one or more hosts, and one or morestorage devices, for management of time locks, in accordance withcertain embodiments.

FIG. 2 illustrates a block diagram that shows elements described by anexemplary time lock, in accordance with certain embodiments;

FIG. 3 illustrates a flowchart that shows generating a point in timecopy of a time locked data set and allowing access to the point in timecopy, in accordance with certain embodiments:

FIG. 4 illustrates a flowchart that shows waiting for a threshold numberof I/O operations to be pending, prior to generating the point in timecopy of a time locked data set, in accordance with certain embodiments;

FIG. 5 illustrates a flowchart that shows a point in time copy beinggenerated for selected regions of the time locked data set after waitingfor a threshold number of I/O operations, in accordance with certainembodiments;

FIG. 6 illustrates a flowchart that shows point in time copy beinggenerated for selected regions of the time locked data set, inaccordance with certain embodiments;

FIG. 7 illustrates a flowchart that shows a reduction of processingoverhead for generating a point in time copy to allow access to timelocked data, in accordance with certain embodiments;

FIG. 8 illustrates a block diagram of a cloud computing environment, inaccordance with certain embodiments;

FIG. 9 illustrates a block diagram of further details of the cloudcomputing environment of FIG. 8, in accordance with certain embodiments;and

FIG. 10 illustrates a block diagram of a computational system that showscertain elements that may be included in the storage controller or thehost, as described in FIGS. 1-9, in accordance with certain embodiments.

DETAILED DESCRIPTION

In the following description, reference is made to the accompanyingdrawings which form a part hereof and which illustrate severalembodiments. It is understood that other embodiments may be utilized andstructural and operational changes may be made.

There may be several reasons for a storage controller to protect datawith a time lock. For example, there may be legal reasons to not allowaccess to data for a certain period of time. In situations where no oneaccesses certain data during certain periods of time, the time lock mayprovide a safety mechanism to prevent a breach of access to the dataduring those times. In certain embodiments, a time lock may be used fordata that is no longer needed for foreseeable future but still needs tobe retained.

A problem with time locks is that while a time lock is active, no useror process may be able to access the time locked data. There may besituations in which a time lock is needed to prevent access to data, butthere may be users or processes that need just a copy of data that theycan access, without having access to the original time locked data.

Certain embodiments provide a storage controller to store data receivedfrom a host. The storage controller provides time lock mechanisms fordata. The storage controller also provides a point in time copy facilityfor the data, where the data is subject to the time lock. In certainembodiments a point in time copy is generated from the data that is tobe time locked, and the point in time copy is allowed to be accessedafter the time lock is active.

When a point in time copy is used to allow access to a copy of the timelocked data, the generation of the point in time copy of a large dataset (e.g., a storage volume) that comprises a time locked data may bevery time consuming.

To provide an efficient mechanism to generate a point in time copy oftime locked data, in certain embodiments a sequence of “N” I/Ooperations (e.g., 1000 I/O operations where N=1000) are allowed toaccumulate prior to performing the point in time copy of the time lockedcopy, and in certain embodiments only regions of the time locked copythat are affected by the “N” I/O operations are copied via point in timecopy operations. In additional embodiments, specific regions (e.g.,selected extents or blocks) of the time locked data are copied via pointin time copy operations when necessary, to allow access to a copy of thetime locked data.

Exemplary Embodiments

FIG. 1 illustrates a block diagram of a computing environment 100comprising a storage controller 102 coupled to one or more hosts 104,106, and one or more storage devices 108, 110, in accordance withcertain embodiments. The storage controller 102 allows the plurality ofhosts 104, 106 to perform input/output (I/O) operations with logicalstorage maintained by the storage controller 102. The physical storagecorresponding to the logical storage may be found in one or more of thestorage devices 108, 110 of the storage controller 102.

The storage controller 102 and the hosts 104, 106 may comprise anysuitable computational device including those presently known in theart, such as, a personal computer, a workstation, a server, a mainframe,a hand held computer, a palm top computer, a telephony device, a networkappliance, a blade computer, a processing device, etc. The storagecontroller 102, the hosts 104, 106, and the storage devices 108, 110 maybe elements in any suitable network, such as, a storage area network, awide area network, the Internet, an intranet. In certain embodiments,the storage controller 102, the hosts 104, 106, and the storage devices108, 110 may be elements in a cloud computing environment that comprisesthe computing environment 100. The storage devices 108, 110 may becomprised of storage disks, tape drives, solid state storage, etc., andmay be controlled by the storage controller 102.

In certain embodiments, a time lock management application 112 thatexecutes in the storage controller 102 may generate one or more timelocks 114 to protect a data set 116 for a predetermined duration oftime. The time lock management application 112 may be implemented insoftware, hardware, firmware or any combination thereof.

In certain embodiments, the time lock management application 112generates a point in time copy 118 of the data set 116. The time lock114 is applied to data set 116 and the point in time copy 118 allowsaccess to I/O operations from the hosts 104, 106. If the data 116 islarge (e.g., a volume or a plurality of volumes) then the point in timecopy 118 may take a significant amount to time and a significant amountto storage space to generate and may impact the performance of thestorage controller 102. Certain embodiments provide mechanisms forefficiently generating the point in time copy 118 from the data set 116.This is performed by copying only selected regions 120 of the data set116 to the point in time copy 118, and/or by waiting to generate thepoint in time copy 118 till a predetermined number of I/O operationsfrom the host 104, 106 are waiting to access the data set 116. Theselected regions 120 of the data set 116 are those blocks or extents orother storage units of the data set 116 that I/O operations attempt toaccess while the data set 116 is time locked.

FIG. 2 illustrates elements described by an exemplary time lock 200 thatin certain embodiments may comprise the time lock 114 shown in FIG. 1.The time lock 200 may indicate volumes [(i.e., logical units (LUNs)]and/or parts of volumes locked by the time lock 200 (as shown viareference numeral 202). For example, in certain embodiments the timelock 200 may indicate that volume A, volume B, and volume C fromlocation X to location Y are locked by the time lock 200. The data set116 with which the time lock 114 is associated may be stored in thevolumes and/or parts of volumes.

The time lock 200 may also indicate the duration for which the time lock200 is in effect (as shown via reference numeral 204). For example, incertain embodiments, the time lock 200 may be in effect every day from10 AM to 8 PM. In other embodiments, the time lock 200 may be in effectfor the whole day every Saturday and Sunday. In still furtherembodiments, the time lock 200 may be in effect from 12 AM Saturday to11:59 PM Sunday. In yet another embodiment, the time lock may be ineffect from Date X onwards (e.g., from Dec. 12, 2017 onwards).

FIG. 3 illustrates a flowchart 300 that shows generating a point in timecopy of a data set and then subjecting the data set to a time lock andallowing access to the point in time copy, in accordance with certainembodiments. The operations shown in FIG. 3 may be performed by the timelock management application 112 that executes in the storage controller102.

Control starts at block 302 in which the time lock managementapplication 112 receives a command to activate a time lock 114 for adata set 116. The time lock management application 112 applies (at block304) the time lock 114 to the data set 116. Control proceeds to block306 in which the time lock management application 112 generates thepoint in time copy 118 of the data set. Subsequent to generation of thepoint in time copy 118, the time lock management application 112 allows(at block 308) access to I/O operations from the host 104, 106 to thepoint in time copy 118.

Therefore, FIG. 3 illustrates certain embodiments in which the data set116 is time locked, and the point in time copy 118 of the data set 116is allowed to be accessed. I/O operations are not allowed access to thetime locked data set 116.

FIG. 4 illustrates a flowchart 400 that shows waiting for a thresholdnumber of I/O operations to be pending prior to generating the point intime copy of a time locked data set, in accordance with certainembodiments. The operations shown in FIG. 4 may be performed by the timelock management application 112 that executes in the storage controller102.

Control starts at block 402 in which the time lock managementapplication 112 receives a command to activate a time lock 114 for adata set 116. The time lock management application 112 applies (at block404) the time lock 114 to the data set 116. As a result, the data set116 is time locked and cannot be accessed to perform I/O operations.

From block 404 control proceeds to block 406 in which the time lockmanagement application 112 receives an I/O operation generated by a hostfor performing I/O on the data set 116. The I/O operation cannot beperformed on the data set 116 that is time locked.

The time lock management application 112 determines (at block 408)whether the number of I/O operations waiting to perform I/O on the timelocked data set 116 exceeds a threshold, where the threshold may be apredetermined number. For example if the predetermined number is N, thenthe time lock management application 112 determines (at block 408)whether the number of I/O operations waiting to perform I/O on the dataset 116 exceeds the number N.

If at block 408 the time lock management application 112 determines (atblock 408) that the number of I/O operations waiting to perform I/O onthe data set 116 does not exceeds the threshold (“No” branch 410) thencontrol proceeds to block 412 where the I/O operation is made to waitand then control returns to block 406 where the next I/O operation isreceived.

If at block 408 the time lock management application 112 determines (atblock 408) that the number of I/O operations waiting to perform I/O onthe data set exceeds the threshold (“Yes” branch 414) then controlproceeds to block 416, in which the time lock management application 112generates the point in time copy 118 of the data set 116. Therefore, thepoint in time copy 118 of the time locked data set 116 is generated onlyafter the number of I/O operations waiting to perform I/O on the dataset 116 exceeds the threshold. As a result, the generation of the pointin time copy 118 is delayed until a sufficient number of I/O operationsare waiting.

Subsequent to generation of the point in time copy 118, the time lockmanagement application 112 performs (at block 418) the waiting I/Ooperations on the point in time copy 118. Further I/O operations on thedata set 116 are redirected (at block 420) to be performed on the pointin time copy 118.

Therefore, FIG. 4 illustrates certain embodiments in which thegeneration of the point in time copy 118 is delayed until the number ofI/O operations are waiting for execution on the time locked data set 116exceeds a predetermined threshold. As a result the relatively timeconsuming generation of the point in time copy 118 is delayed until itbecomes necessary to execute the waiting I/O operations.

FIG. 5 illustrates a flowchart 500 that shows a point in time copy 118being generated for selected regions 120 of the time locked data set 116after waiting for a threshold number of I/O operations, in accordancewith certain embodiments. The operations shown in FIG. 5 may beperformed by the time lock management application 112 that executes inthe storage controller 102.

Control starts at block 502 in which the time lock managementapplication 112 receives a command to activate a time lock for a dataset 116. The time lock management application 112 applies (at block 504)the time lock 114 to the data set 116. As a result, the data set 116 istime locked and cannot be accessed to perform I/O operations.

From block 504 control proceeds to block 506 in which the time lockmanagement application 112 receives an I/O operation generated by a hostfor performing I/O on the data set 116. The I/O operation cannot beperformed on the data set 116 that is time locked.

The time lock management application 112 determines (at block 508)whether the number of I/O operations waiting to perform I/O on the dataset 116 exceeds a threshold, where the threshold may be a predeterminednumber. For example if the predetermined number is N, then the time lockmanagement application 112 determines (at block 508) whether the numberof I/O operations waiting to perform I/O on the data set exceeds thenumber N.

If at block 508 the time lock management application 112 determines thatthe number of I/O operations waiting to be performed I/O on the data setdoes not exceeds the threshold (“No” branch 510) then control proceedsto block 512 where the I/O operation is made to wait and then controlreturns to block 506 in which the next I/O operation is received.

If at block 508 the time lock management application 112 determines thatthe number of I/O operations waiting to perform I/O on the data setexceeds the threshold (“Yes” branch 514) then control proceeds to block516, in which the time lock management application 112 generates thepoint in time copy of selected regions 120 (e.g., extents, blocks) ofthe time locked data set 116 where the I/O operations are waiting to beperformed on the selected regions 120 of the time locked data set 116.Therefore, the point in time copy 118 of the time locked data set 116 isgenerated not only after the number of I/O operations waiting to performI/O on the data set 116 exceeds the threshold, but the point in timecopy 118 is performed only on selected regions 120 on the time lockeddata set 116. As a result, the generation of the point in time copy 118is delayed until a sufficient number of I/O operations are waiting andthe point in time copy 118 is performed much faster in comparison togenerating the point in time copy of the entirety of the time lockeddata set 116.

Subsequent to generation of the point in time copy 118, the time lockmanagement application 112 performs (at block 518) the waiting I/Ooperations on the point in time copy 118 of the selected regions 120 ofthe time locked data set 116, and control returns to block 506 forreceiving additional I/O operations.

Therefore, FIG. 5 illustrates certain embodiments in which point in copy118 is generated only for selected regions 120 of the data set 116 onwhich a predetermined number of I/O operations are waiting to beperformed.

FIG. 6 illustrates a flowchart 600 that shows point in time copy beinggenerated for selected regions 120 of the time locked data set 116, inaccordance with certain embodiments. The operations shown in FIG. 6 maybe performed by the time lock management application 112 that executesin the storage controller 102.

Control starts at block 602 in which the time lock managementapplication 112 receives a command to activate a time lock for a dataset 116. The time lock management application 112 applies (at block 604)the time lock 114 to the data set 116. Control proceeds to block 606 inwhich the time lock management application 112 receives an I/O operationfor performing an I/O on the data set 116, and then generates (at block608) the point in time copy of selected regions 120 (e.g., extents,blocks, etc.) of the data set 116, where the I/O operation is for theselected regions.

Subsequent to generation of the point in time copy of the selectedregions of the time locked data set 116, the time lock managementapplication 112 performs (at block 610) the I/O operations on the pointin time copy 118 of the selected regions 120 of the time locked data set116.

Therefore, FIG. 6 illustrates certain embodiments in which the data set116 is time locked, and processing time for generation of point in timecopy 118 is reduced by generating only the point in time copy of thoseregions of the time locked data set on which I/O operations arerequested to be performed.

FIG. 7 illustrates a flowchart 700 that shows a reduction of processingoverhead for copying data to allow access to time locked data, inaccordance with certain embodiments. The operations shown in FIG. 7 maybe performed by the time lock management application 112 that executesin the storage controller 102.

Control starts a block 702 in which a computational device (e.g.,storage controller 102) generates a point in time copy 118 of one ormore regions (e.g., selected regions 120) of a time locked data set 116,in response to receiving one or more I/O operations (e.g., apredetermined number of I/O operations) directed to the time locked dataset 116. In certain embodiments, the one or more regions comprise anentirety of the time locked data set, and in other embodiments, the oneor more regions comprise those regions of the time locked data set towhich the I/O operations are directed. The one or more regions mayinclude one or more volumes or parts of volumes. In certain embodiments,the generating of the point in time copy of the one or more regions ofthe time locked data set is performed subsequent to the one or more I/Ooperations exceeding a predetermined threshold number. It may be notedthat the computational device 102 prevents the I/O operations from beingperformed on the time locked data set 116.

From block 702 control proceeds to block 704 in which the one or moreI/O operations are performed on the point in time copy of the one ormore regions 120 of the time locked data set 116, in response togenerating the point in time copy 118 of the one or more regions 120 ofthe time locked data set 116.

From block 704 control proceeds to block 706, in which on expiry of atime lock 114 on the time locked data set 116, additional I/O operationsare directed to the previously time locked data set 116 that is now nolonger subject to the time lock, and not directed to the point in timecopy.

Therefore FIGS. 1-7 illustrate certain embodiments in which a point intime copy of a time locked data set is performed by waiting until apredetermined number of I/O operations are waiting for accessing thetime locked data set. Furthermore, in certain embodiments only theregions of the data set that are to be accessed are subjected to thepoint in time copy operations.

Cloud Computing Environment

Cloud computing is a model for enabling convenient, on-demand networkaccess to a shared pool of configurable computing resources (e.g.,networks, servers, storage, applications, and services) that can berapidly provisioned and released with minimal management effort orservice provider interaction.

Referring now to FIG. 8, an illustrative cloud computing environment 50is depicted. As shown, cloud computing environment 50 comprises one ormore cloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 8 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 9, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 8) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 9 are intended to be illustrative only and embodiments of theinvention are not limited thereto.

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include mainframes, in oneexample IBM zSeries* systems; RISC (Reduced Instruction Set Computer)architecture based servers, in one example IBM pSeries* systems; IBMxSeries* systems; IBM BladeCenter* systems; storage devices; networksand networking components. Examples of software components includenetwork application server software, in one example IBM WebSphere*application server software; and database software, in one example IBMDB2* database software. * IBM, zSeries, pSeries, xSeries, BladeCenter,WebSphere, FlashCopy, and DB2 are trademarks of International BusinessMachines Corporation registered in many jurisdictions worldwide.

Virtualization layer 62 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers;virtual storage; virtual networks, including virtual private networks;virtual applications and operating systems; and virtual clients.

In one example, management layer 64 may provide the functions describedbelow. Resource provisioning provides dynamic procurement of computingresources and other resources that are utilized to perform tasks withinthe cloud computing environment. Metering and Pricing provide costtracking as resources are utilized within the cloud computingenvironment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal provides access to the cloud computing environment forconsumers and system administrators. Service level management providescloud computing resource allocation and management such that requiredservice levels are met. Service Level Agreement (SLA) planning andfulfillment provide pre-arrangement for, and procurement of, cloudcomputing resources for which a future requirement is anticipated inaccordance with an SLA.

Workloads layer 66 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation; software development and lifecycle management; virtualclassroom education delivery; data analytics processing; transactionprocessing; and time lock processing 68 as shown in FIGS. 1-9.

Additional Embodiment Details

The described operations may be implemented as a method, apparatus orcomputer program product using standard programming and/or engineeringtechniques to produce software, firmware, hardware, or any combinationthereof. Accordingly, aspects of the embodiments may take the form of anentirely hardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,aspects of the embodiments may take the form of a computer programproduct. The computer program product may include a computer readablestorage medium (or media) having computer readable program instructionsthereon for causing a processor to carry out aspects of the presentembodiments.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present embodiments may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present embodiments.

Aspects of the present embodiments are described herein with referenceto flowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instruction.

FIG. 10 illustrates a block diagram that shows certain elements that maybe included in the storage controller 102, the hosts 104, 106, or othercomputational devices in accordance with certain embodiments. The system1000 may include a circuitry 1002 that may in certain embodimentsinclude at least a processor 1004. The system 1000 may also include amemory 1006 (e.g., a volatile memory device), and storage 1008. Thestorage 1008 may include a non-volatile memory device (e.g., EEPROM.ROM, PROM, flash, firmware, programmable logic, etc.), magnetic diskdrive, optical disk drive, tape drive, etc. The storage 1008 maycomprise an internal storage device, an attached storage device and/or anetwork accessible storage device. The system 1000 may include a programlogic 1010 including code 1012 that may be loaded into the memory 1006and executed by the processor 1004 or circuitry 1002. In certainembodiments, the program logic 1010 including code 1012 may be stored inthe storage 1008. In certain other embodiments, the program logic 1010may be implemented in the circuitry 1002. One or more of the componentsin the system 1000 may communicate via a bus or via other coupling orconnection 1014. Therefore, while FIG. 10 shows the program logic 1010separately from the other elements, the program logic 1010 may beimplemented in the memory 1006 and/or the circuitry 1002.

Certain embodiments may be directed to a method for deploying computinginstruction by a person or automated processing integratingcomputer-readable code into a computing system, wherein the code incombination with the computing system is enabled to perform theoperations of the described embodiments.

The terms “an embodiment”, “embodiment”, “embodiments”, “theembodiment”, “the embodiments”, “one or more embodiments”, “someembodiments”, and “one embodiment” mean “one or more (but not all)embodiments of the present invention(s)” unless expressly specifiedotherwise.

The terms “including”, “comprising”, “having” and variations thereofmean “including but not limited to”, unless expressly specifiedotherwise.

The enumerated listing of items does not imply that any or all of theitems are mutually exclusive, unless expressly specified otherwise.

The terms “a”, “an” and “the” mean “one or more”, unless expresslyspecified otherwise.

Devices that are in communication with each other need not be incontinuous communication with each other, unless expressly specifiedotherwise. In addition, devices that are in communication with eachother may communicate directly or indirectly through one or moreintermediaries.

A description of an embodiment with several components in communicationwith each other does not imply that all such components are required. Onthe contrary a variety of optional components are described toillustrate the wide variety of possible embodiments of the presentinvention.

Further, although process steps, method steps, algorithms or the likemay be described in a sequential order, such processes, methods andalgorithms may be configured to work in alternate orders. In otherwords, any sequence or order of steps that may be described does notnecessarily indicate a requirement that the steps be performed in thatorder. The steps of processes described herein may be performed in anyorder practical. Further, some steps may be performed simultaneously.

When a single device or article is described herein, it will be readilyapparent that more than one device/article (whether or not theycooperate) may be used in place of a single device/article. Similarly,where more than one device or article is described herein (whether ornot they cooperate), it will be readily apparent that a singledevice/article may be used in place of the more than one device orarticle or a different number of devices/articles may be used instead ofthe shown number of devices or programs. The functionality and/or thefeatures of a device may be alternatively embodied by one or more otherdevices which are not explicitly described as having suchfunctionality/features. Thus, other embodiments of the present inventionneed not include the device itself.

At least certain operations that may have been illustrated in thefigures show certain events occurring in a certain order. In alternativeembodiments, certain operations may be performed in a different order,modified or removed. Moreover, steps may be added to the above describedlogic and still conform to the described embodiments. Further,operations described herein may occur sequentially or certain operationsmay be processed in parallel. Yet further, operations may be performedby a single processing unit or by distributed processing units.

The foregoing description of various embodiments of the invention hasbeen presented for the purposes of illustration and description. It isnot intended to be exhaustive or to limit the invention to the preciseform disclosed. Many modifications and variations are possible in lightof the above teaching. It is intended that the scope of the invention belimited not by this detailed description, but rather by the claimsappended hereto. The above specification, examples and data provide acomplete description of the manufacture and use of the composition ofthe invention. Since many embodiments of the invention can be madewithout departing from the spirit and scope of the invention, theinvention resides in the claims hereinafter appended.

What is claimed is:
 1. A method, comprising: generating, by acomputational device, a point in time copy of one or more regions of atime locked data set, in response to receiving one or more Input/Output(I/O) operations directed to the time locked data set; and performingthe one or more I/O operations on the point in time copy of the one ormore regions of the time locked data set, in response to generating thepoint in time copy of the one or more regions of the time locked dataset.
 2. The method of claim 1, wherein the one or more regions comprisean entirety of the time locked data set.
 3. The method of claim 1,wherein the one or more regions comprise those regions of the timelocked data set to which the I/O operations are directed.
 4. The methodof claim 1, wherein the generating of the point in time copy of the oneor more regions of the time locked data set is performed subsequent tothe one or more I/O operations exceeding a predetermined thresholdnumber.
 5. The method of claim 1, the method further comprising:preventing the I/O operations from being performed on the time lockeddata set.
 6. The method of claim 1, wherein the one or more regionsinclude one or more volumes or parts of volumes in which the time lockeddata set is stored.
 7. The method of claim 1, wherein on expiry of atime lock on the time locked data set, additional I/O operations aredirected to the time locked data set and not directed to the point intime copy.
 8. A system, comprising: a memory; and a processor coupled tothe memory, wherein the processor performs operations, the operationscomprising: generating a point in time copy of one or more regions of atime locked data set, in response to receiving one or more Input/Output(I/O) operations directed to the time locked data set; and performingthe one or more I/O operations on the point in time copy of the one ormore regions of the time locked data set, in response to generating thepoint in time copy of the one or more regions of the time locked dataset.
 9. The system of claim 8, wherein the one or more regions comprisean entirety of the time locked data set.
 10. The system of claim 8,wherein the one or more regions comprise those regions of the timelocked data set to which the I/O operations are directed.
 11. The systemof claim 8, wherein the generating of the point in time copy of the oneor more regions of the time locked data set is performed subsequent tothe one or more I/O operations exceeding a predetermined thresholdnumber.
 12. The system of claim 8, the operations further comprising:preventing the I/O operations from being performed on the time lockeddata set.
 13. The system of claim 8, wherein the one or more regionsinclude one or more volumes or parts of volumes in which the time lockeddata set is stored.
 14. The system of claim 8, wherein on expiry of atime lock on the time locked data set, additional I/O operations aredirected to the time locked data set and not directed to the point intime copy.
 15. A computer program product, the computer program productcomprising a computer readable storage medium having computer readableprogram code embodied therewith, the computer readable program codeconfigured to perform operations on a processor of a computationaldevice, the operations comprising: generating, by the computationaldevice, a point in time copy of one or more regions of a time lockeddata set, in response to receiving one or more Input/Output (I/O)operations directed to the time locked data set; and performing the oneor more I/O operations on the point in time copy of the one or moreregions of the time locked data set, in response to generating the pointin time copy of the one or more regions of the time locked data set. 16.The computer program product of claim 15, wherein the one or moreregions comprise an entirety of the time locked data set.
 17. Thecomputer program product of claim 15, wherein the one or more regionscomprise those regions of the time locked data set to which the I/Ooperations are directed.
 18. The computer program product of claim 15,wherein the generating of the point in time copy of the one or moreregions of the time locked data set is performed subsequent to the oneor more I/O operations exceeding a predetermined threshold number. 19.The computer program product of claim 15, the operations furthercomprising: preventing the I/O operations from being performed on thetime locked data set.
 20. The computer program product of claim 15,wherein the one or more regions include one or more volumes or parts ofvolumes in which the time locked data set is stored.
 21. The computerprogram product of claim 15, wherein on expiry of a time lock on thetime locked data set, additional I/O operations are directed to the timelocked data set and not directed to the point in time copy.
 22. Astorage controller, wherein the storage controller is configured toperform operations, the operations comprising: generating a point intime copy of one or more regions of a time locked data set, in responseto receiving one or more Input/Output (I/O) operations directed to thetime locked data set; and performing the one or more I/O operations onthe point in time copy of the one or more regions of the time lockeddata set, in response to generating the point in time copy of the one ormore regions of the time locked data set.
 23. The storage controller ofclaim 22, wherein the one or more regions comprise an entirety of thetime locked data set.
 24. The storage controller of claim 22, whereinthe one or more regions comprise those regions of the time locked dataset to which the I/O operations are directed.
 25. The storage controllerof claim 22, wherein the generating of the point in time copy of the oneor more regions of the time locked data set is performed subsequent tothe one or more I/O operations exceeding a predetermined thresholdnumber.
 26. The storage controller of claim 22, the operations furthercomprising: preventing the I/O operations from being performed on thetime locked data set.
 27. The storage controller of claim 22, whereinthe one or more regions include one or more volumes or parts of volumesin which the time locked data set is stored.
 28. The storage controllerof claim 22, wherein on expiry of a time lock on the time locked dataset, additional I/O operations are directed to the time locked data setand not directed to the point in time copy.